Rely on noMoreOperators for dynamic filters collection#12594
Rely on noMoreOperators for dynamic filters collection#12594losipiuk merged 1 commit intotrinodb:masterfrom
Conversation
Relying on noMoreOperators from DynamicFilterSourceOperatorFactory for detecting completion of dynamic filter collection will simplify the implementation for fault tolerant execution where the collection may take place in a source stage.
9303c63 to
36b8c04
Compare
|
Can it increase DF collection latency? |
Normally |
I think we can bail-out faster before |
I've run TPC benchmarks and confirmed no regressions. Let me know if you have any input about the code or any problematic scenarios in mind. |
Nope. Just wanted to confirm latency is not harmed |
| import io.trino.spi.predicate.TupleDomain; | ||
| import io.trino.sql.planner.plan.DynamicFilterId; | ||
|
|
||
| public interface DynamicFilterSourceConsumer |
There was a problem hiding this comment.
nit: DynamicFilterConsumer, or maybe simply drop this interface and override the method you need for testing?
|
Do we want a release notes entry for this? |
This is just an internal refactoring, no user facing change |
Relying on noMoreOperators from DynamicFilterSourceOperatorFactory
for detecting completion of dynamic filter collection will simplify
the implementation for fault tolerant execution where the collection
may take place in a source stage.